Request to hand over a session between a mobile communication device and a customer premises equipment

ABSTRACT

Methods, systems, and apparatus can be used to provide handover of on-hold sessions in converged networks. In various example implementations, an on-hold session between a mobile communication device and a fixed packet network-connected peer CPE can be handed over from a fixed packet domain to a cellular domain, and vice versa. In various example implementations, an on-hold session between a mobile communication device and a PSTN-connected peer CPE can be handed over from a fixed packet domain to a cellular domain, and vice versa.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/861,727 titled “Handover of On-Hold Session Between Fixed PacketNetwork and Cellular Network,” which was filed on Jan. 4, 2018. U.S.application Ser. No. 15/861,727 is a continuation of U.S. applicationSer. No. 13/631,404 titled “Handover of On-Hold Session Between FixedPacket Network and Cellular Network,” which was filed on Sep. 28, 2012.U.S. application Ser. No. 13/631,404 is a nonprovisional applicationclaiming the benefit of U.S. Provisional Application Ser. No. 61/618,255titled “Fixed Mobile Convergence (FMC)—Example Implementations,” whichwas filed on Mar. 30, 2012. The entirety of U.S. application Ser. Nos.15/861,727, 13/631,404, and U.S. Provisional Application Ser. No.61/618,255 is hereby incorporated by reference.

TECHNICAL FIELD

This disclosure relates to the handover of sessions between domains.

BACKGROUND

With the advent of modern communications, a variety of communicationsmodalities and devices exist within a user's premises. Traditionally,customers made (and still make) telephone calls via the public switchedtelephone network (PSTN). Many data communications modalities exist,including several packet-based communications solutions that providebroadband access to the Internet and World Wide Web using, for example,Internet Protocol (IP). These include digital subscriber line service(s)offered through telcos, and data over cable services (e.g., broadbandservices over the networks traditionally provided by cable televisionoperators). Although these packet-based broadband IP networks have beenreferred to as “fixed” because of the lack of mobility of theon-premises access point, these networks can still include the use ofwireless technology. For example, wireless communications can beincorporated in the delivery infrastructure of the fixed packet network(such as satellite or radio transmission towers), and fixed packetnetworks can also be accessed via a local wireless network (whichtypically has limited range) such as a Wi-Fi™ (i.e., wireless) network.

These fixed packet networks have also allowed users to make telephonecalls (voice calls) over them using by carrying voice packets over thefixed packet networks. This technology includes, for example, Voice overIP (VoIP) technology on a broadband IP network.

In concurrent developments, mobile/cellular communications devices, suchas mobile handsets, have become ubiquitous in modern society. Mobilecommunications devices such as “smartphones” can allow users to maketelephone calls, send or receive electronic mail (e-mail), browse theWorld Wide Web, check appointments, and get directions, as well asperform many other functions. Such mobile devices typically use cellularnetworks to handle telephone calls. However, cellular networks oftenvary in quality and coverage area. It is typical for users having acellular phone service to discontinue a phone call on their mobiledevice and start another call using a fixed communications phone, suchas a POTS phone (e.g., telephone connected to the PSTN) or VoIP phone,to communicate once the users are in their premises.

With the rise of VoIP and mobile/cellular networks, fixed-mobileconvergence (FMC) represents an aim by the telecommunications industryto allow transitions between the fixed packet network communicationsdomain and the mobile domain. As an example of such an FMC process, auser's in-progress communication session, which may be a voice call, canmove from communicating through the mobile (i.e., cellular) network tocommunicating through a fixed packet network while the user is on thesame mobile phone, and vice versa. This “handover” from a cellulardomain to fixed domain (and vice versa) preferably occurs without anysignificant interruption or disconnection in the communication sessionnoticeable by either user. The FMC network can allow, for example, auser that initiates a cellular phone call on his or her handset out ofthe premises to continue with the same call on the same handset, but onthe fixed packet network, when the user arrives in his/her home.Conversely, if a user having a mobile handset places a call over thefixed packet network via the fixed packet network's wireless accesspoint, and the signal to the wireless access point signal for the fixedpacket network degrades (for example if the user moves outside thepremises), a FMC service should allow the user to continue with thecommunication on the same mobile handset over the cellular network.

Implementations described in this disclosure provide for the handover oftwo sessions initiated by a user having a mobile communication device,wherein one session is active, and the other session is on hold. In thecase of a session that is voice, an on-hold session would typically be alogical state in which neither user of the session can hear the other.Additionally, this disclosure provides for the handover of an on-holdsession in which the on-hold session is between a mobile handset deviceand a peer CPE device connected to a fixed packet network, or between amobile handset device and a peer CPE device connected to a PSTN network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example network environmentoperable to provide handover of sessions in converged networks.

FIG. 2 is a flow chart illustrating an example process that can beperformed by a mobility application server to facilitate the transfer ofan on-hold session between a mobile communications device and peer CPEconnected to a fixed packet network.

FIG. 3 is a sequence diagram illustrating an example implementation of ahandover process of an on-hold session between a mobile communicationsdevice and peer CPE connected to a fixed packet network.

FIG. 4 is a sequence diagram illustrating another example implementationof a handover process of an on-hold an on-hold session between a mobilecommunications device and peer CPE connected a fixed packet network.

FIG. 5 is flow chart illustrating an example process that can beperformed by a mobile communication device to enable on-hold featuresbetween a mobile communications device and peer CPE connected to a fixedpacket network.

FIG. 6 is a block diagram illustrating an example of a hardware devicethat can be used to process the handover of an on-hold session between amobile communications device and peer CPE connected to an IP network.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

In some implementations of this disclosure, systems and methods canoperate to provide communication session handovers between fixed andcellular domains. This disclosure describes various implementations ofsystems and methods of a fixed mobile convergence network that canprovide for the handover of an on-hold session, including a handover ofthe session from the fixed packet network to the mobile network. Theon-hold session can be an on-hold session between an FMC enabled mobilecommunications device and a CPE device connected to a fixed packetnetwork, or on-hold session can be between an FMC enabled mobilecommunications device and a CPE device connected to a PSTN. Thecomponents used in supporting this feature can include a mobilityapplication server (MAS) operable to facilitate connections between amobile communications device and user devices connected to a cellularnetwork, PSTN network, or a fixed packet network (e.g., a broadband IPnetwork). The following disclosure describes various implementations andchanges operable to facilitate the session handover features in moredetail.

FIG. 1 is a block diagram illustrating an example fixed-mobile convergedservices network environment 100 operable to provide handover of one ormore sessions in converged networks. The handover can occur betweendomains using handover public service identities (PSIs), wherein one ofthe sessions is, for example, an on-hold session between a mobile deviceand a CPE (e.g., a cable telephony modem) having a communications deviceconnected to an IP network, and the other session is an active session.In some implementations, a mobility application server (MAS) 105 isoperable to serve as a converged services platform that interconnectsand routs communications to user devices, which can be connected to acellular network 110, a fixed packet network 115, or a PSTN network 120.

The cellular network 115 can include a number of mobile communicationsdevices 115 a-d, 130 that communicate with cellular towers. Each of thecellular towers can communicate with mobile communications devices 115a-d, 130 in a cell assigned to that cellular tower. Mobilecommunications devices 115 a-d, 130 can communicate with the cellulartowers via wireless links 135 a-e. The cellular network can be of anyvariety, including a Global System for Mobile communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), Code Division multiple access (CDMA) system, General Packet RadioService (GPRS), Evolution-Data Optimized (EV-DO), Enhanced Data Ratesfor GSM Evolution (EDGE), 3GSM, Digital Enhanced CordlessTelecommunications (DECT), Digital AMPS (IS-136/TDMA), and IntegratedDigital Enhanced Network (iDEN). Typical multiplexing schemes used bythese networks can include, among others, frequency division (FDM), timedivision multiple access (TDM), code division multiplex (CDM), and spacedivision multiplex (SDM), each of which can use appropriate accessschemes (e.g., FDMA, TDMA, CDMA, and SDMA). Mobile devices 115 a-d, 130can include cellphones, smartphones, portable computing devices, as wellas other devices capable of carrying data and voice.

The fixed packet network 115 can be, for example, a network acommunications network capable of using packets to deliver video, voice,and data. Fixed packet networks can include broadband networks such asthose that deliver data using internet protocol (IP). An example of sucha network is a cable television (CATV) infrastructure implementing thedata over cable service interface specification (DOCSIS) and PacketCablestandards. In some implementations, the fixed packet network can haveheadend equipment such as a cable modem termination system (CMTS) thattransmits and receives communications through one or more hybrid fibercoax (HFC) networks to CPE devices 140 a-d. The headend, HFC network(s),and CPE devices 140 a-d can be provided by multiple service operators(MSOs) that provide community cable television service to users. The CPE140 a-d, each of which has its own MAC address, can include cable modems(CMs), cable telephony modems (a.k.a. embedded multi-media terminal orEMTA devices), and on-premises gateways. Telephones and other computingdevices can be connected to the cable modems or EMTAs. Additionally, CPEdevices 140 a-d can have the functionality of telephones or othercomputing devices integrated into the CPE device 140 a-d. The CPE 140a-d can also be connected to a wireless local area network (WLAN)device, such as, for example, wireless access point 145. Wireless accesspoint 145 can be a wireless router that operates in accordance with theIEEE 802.11 family of standards and serve as an access point to thefixed packet network 115 for a computing device (e.g., personalcomputer, laptop, or tablet), or a multi-modal handset device asreferred to below. Alternatively, the CPE 140 a-d can have internalwireless routing functionality incorporated into it.

The fixed packet network 115 can also include networks usingasynchronous transfer mode (ATM), digital subscriber line (DSL), orasymmetric digital subscriber line (ADSL) technology. These networkshave typically been provided by telephone companies (telcos). ATM andDSL/ADSL equipment can be located at an exchange or central office, andcan include integrated DSL/ATM switches, multiplexers such as digitalsubscriber line access multiplexers (DSLAMS), and broadband remoteaccess servers (B-RAS), all of which can contribute to the aggregationof communications from user equipment onto a high-capacity uplink (ATMor Gigabit Ethernet backhaul) to internet service providers (ISPs).Transmission media connecting the central office and user equipment caninclude both twisted pair and fiber. For the user to access the DSLnetwork, customer premises equipment 140 a-d (each of which can have itsown MAC address), can include, for example, a DSL modem. The DSL modemcan also include wireless routing functionality or can be connected to awireless access point (examples of which were discussed above).

In addition to data over cable and DSL based solutions as describedabove, the fixed packet network(s) 115 can also be provided via legacyT1/T3 lines, or WiMAX™ networks implementing the IEEE 802.16 family ofwireless networking standards, or any combination of those packetswitched networks described herein or known in the industry.

FIG. 1 also illustrates a PSTN network 120, having customer premisesdevices 150 a-d, such as telephones and computers, connected to the PSTN120. The PSTN 120 can be connected to the cellular network 110 and thefixed packet network 115 via the mobility application server 105.

In example implementations, mobile communication device 130 (e.g., whichcan also be referred to herein as a FMC mobile device 130), can includeclient software that facilitates its operation as a multi-modal handsetthat can communicate via both a cellular network and via a fixed packetnetwork. For example, the mobile communication device 130 cancommunicate via cellular network 110, using wireless link 135 e.Wireless link 135 e can include IP, GSM, LTE, Wi-MAX™ (i.e., WorldwideInteroperability for Microwave Access), Wi-Fi™ (i.e., wireless), or CDMAlinks. As another example, FMC mobile device 130 can access fixed packetnetwork 115, by communicating with the wireless access point 145 viawireless data link 155. The FMC mobile device 130 can also be operableto transmit communications and perform functions relating to theon-hold/off-hold and handover functions described herein.

In example implementations, a mobile communications device 130 can beoperable to communicate with the MAS 105. The MAS 105 can handlemessaging and routing between the cellular network 110, fixed packetnetwork 115, and the PSTN 120. The MAS 105 can be a computing devicehaving software that makes it operable to provide the functionalitiesdescribed herein. In example implementations, the MAS 105 can beoperable to process signaling protocols, for example SIP, and handlesession setup, session connect, session management, and sessionteardown. The MAS 105, operating as a SIP server, can function as one ormore of a registrar server, a location service database, a redirectserver, a proxy server, or a presence server. The MAS 105 can be placedor reside on any of the networks (e.g., within a headend of the fixedpacket network 115).

In some implementations, the MAS 105 can perform gateway functions.Gateways that link fixed packet network with a PSTN, a PSTN with acellular network, and an IP network with the cellular network aretypically deployed and used to route communications, including voice,between the different types of networks. The MAS 105 can process one ormore signaling protocols, including but not limited to SIP, SIP-T, GSM,CDMA, MAP, and SS7. For example, in instances in which a session isrouted from fixed packet network 115 to the PSTN 120, or a session isrouted from the PSTN 120 to fixed packet network 115, the MAS 105 can beused to translate communication protocols (for example, IP to TDM)between the networks. The MAS 105 can be operable to convert packetbased voice (e.g., VoIP) communications to circuit switched voice fortransmission on the PSTN 120, and can convert circuit switched voice topacket based voice communications for transmission onto a fixed packetnetwork 115. In example implementations using Session InitiationProtocol (SIP) communications, SIP universal resource identities (URIs)can be used to carry telephone numbers, since the mapping between SIPand telephony protocols has already been defined.

The MAS 105 can facilitate routing of communications with the FMC mobiledevice 130 through the use of a location service and location servicedatabase, which can periodically receive updates (e.g., a locationbeacon) from the mobile communications device 130. The location serviceidentifies the location (e.g., cell) associated with the FMC mobiledevice 130 and stores the location information in a current locationstore such that incoming sessions destined for the mobile communicationsdevice 130 can be properly routed. Thus, for example, an incomingsession can be routed to a cellular tower close in proximity to themobile communications device 130 (e.g., the cellular tower responsiblefor the cell from which the last beacon signal was received).

In example implementations, the MAS 105 can also be operable to functionas a proxy server by processing, for example, SIP requests and passingthe request downstream, as well as sending SIP responses upstream toother SIP servers or devices. The MAS 105 can also modify SIP requests,and enable the setup, teardown, and modification of communicationssessions.

In example implementations, when a wireless data link 155 is available,the mobile communications device 130 can communicate with the MAS 105through the fixed packet network 115 via the wireless access point 145and the wireless data link 155. In the case of a voice call, the mobilecommunications device can be operable to send and receive voice packetsthrough the fixed packet network 115. The FMC mobile device 130 can alsoinitiate a communication session through the cellular network 110 viacommunications link 135.

As mentioned above, once a request for a session has been made by theFMC mobile device 130, the MAS 105 can be operable to facilitate theestablishment, teardown, or modification of sessions between FMC mobiledevice 130 and other peer devices, including mobile devices 115 a-d, CPEdevices 140 a-c connected to the fixed packet network 115 (e.g., whichcan be referred to herein as FPN peer CPE 140 a-c), and/or CPE devices150 a-d connected to the PSTN 120 (e.g., which can be referred to hereinas PSTN peer CPE 150 a-d).

As an example, FMC mobile device 130 can initiate a session via thecellular network 110 with a FPN peer CPE 140 a-c. As mentioned above,the FPN peer CPE 140 a-c can include a cable modem, a DSL modem, an ADSLmodem, an E-MTA, a gateway, or the like, and computing devices ortelephones can be attached to FPN peer CPE 140 a-c. The FMC mobiledevice 130 can send an active session request (e.g., a session setuprequest) through the cellular network 110 to the MAS 105. The MAS 105,upon receiving the request, facilitates the session setup between themobile communications device 130 and the FPN peer CPE 140 a-c. For theactive session, the MAS 105 can create an anchor point establishing twoconnections points for the session—one connection point for the MAS-FMCmobile device 130 through the cellular network 110 connection, andanother connection point for the MAS-FPN peer CPE 140 a-c through thefixed packet network 115 connection. In the instance whereby thecommunications are between the FMC mobile device 130 and a PSTN peer CPE150 a-d, the MAS 105 can establish an active session, anchoring thesession with a connection point for the MAS-FMC mobile device 130through the cellular network 110, and a connection point for theMAS-PSTN peer 150 a-d through the PSTN 120 connection. Similarly, asession can be established via the MAS 105 between the FMC mobile device130 and another mobile device 115 a-d on the cellular network (which canalso be referred to as cellular peer 115 a-d). Additionally, the MAS 105can establish sessions based on requests from any of the aforementioneduser devices that are directed to the FMC mobile device 130. Someexample implementations of an active session establishment process canbe found in U.S. Pat. No. 8,244,251 titled “Concurrent Call Handover,”the entirety of which is hereby incorporated by reference.

In an example in which a session has been established through thecellular network 110, the MAS 105 can be operable to accept and handlethe handover of the session from the cellular network 110 to the fixedpacket network 115. This linking of the home wireless local area networkand a user's FMC mobile device 130 provides convenience when FMC mobiledevice 130 is within the range of the user's on-premises wireless LAN.Handovers from the cellular network 110 to the fixed packet network 115can also be seen as a way to offload session traffic from the cellularnetwork 110 to the fixed packet network 115. Additionally, voicesessions through the fixed packet network 115 can have more clarity, insome instances.

An example of a handover process can be illustrated when a sessionbetween FMC mobile device 130 and PSTN peer CPE 150 a has already beenestablished through the cellular domain (i.e., over the cellular network110). When FMC mobile device 130 enters the wirelesstransmission/reception range of local wireless access point 145 (e.g.,which can be a Wi-Fi™ (i.e., wireless) router used to establish anon-premises wireless local area network (WLAN)), a handover request canbe initiated by the FMC mobile device 130.

In some implementations, the FMC mobile device 130 can be registered orassociated with the WLAN. Typical wireless routers can continuouslygenerate a signal (e.g., a beacon), which can be referred to as apresence signal, indicating that the wireless network is active. Thissignal, which can be received by the FMC mobile device 130, typicallyincludes an identifier, such as the Basic Service Set Identifier(BSSID), which is a unique identifier related to the MAC address of thewireless access point 145.

Upon receiving the presence signal from wireless access point 145, theFMC mobile device 130 can be operable to transmit the BSSID of wirelessaccess point 145 to the MAS 105. The BSSID can be transmitted by themobile communications device 130 via, for example, a SIP message throughthe fixed packet network 115. Another mechanism for transporting BSSIDinformation corresponding to the wireless network in which the FMCmobile device 130 is currently present may include usingP-Access-Network-Info which is known in the art for transmitting networktype. It will be appreciated that other formats/protocols may also beused to transmit/forward the BSSID of the WLAN to the MAS 105. When theMAS 105 receives a handover request (e.g., including the handover PSI,appropriate identifiers for the WLAN network, FMC user accountinformation for the mobile communications device 105) from the FMCmobile device 130, the MAS 105 processes the request. The processing caninclude updating dynamic databases, request authentication, andperforming the handover via the fixed packet network 115, as describedabove.

Prior to the handover, the anchor point for the session would have twoconnection points—one for the MAS-FMC mobile device 130 through thecellular network 110, and the other for the MAS-PSTN peer CPE 150 a-dthrough the PSTN 120. After the handover, the anchor point would featurethe MAS-FMC mobile device 130 connection point through the fixed packetnetwork 115, while the MAS-PSTN peer CPE 150 a-d connection pointthrough the PSTN 120 is maintained.

Conversely, communications established through the wireless data link155 have a limited range. The MAS 105 can operate to handover sessionsbetween an IP network and the cellular network 110 using the PSIsassociated with the session. Thus, when a user moves his/her FMC mobiledevice 130 out of range of a wireless access point 145, the MAS 105 cankeep the session open and establish a connection to the FMC mobiledevice 130 via the cellular network 110.

In some implementations, if the FMC mobile device 130 moves out of rangeof the wireless access point 145, and into range of another wirelessaccess point (not shown), the session can be routed through the fixedpacket network 115 by using the new wireless access point, including awireless access point at another location (provided the FMC device 130has authority to access that wireless access point). Thus, the MAS 105can facilitate session handoff between multiple different wirelessaccess points.

In some implementations, the MAS 105 can keep track of two PSI sessionidentifiers and the FMC mobile device 130 can be provisioned formultiple PSIs, thereby facilitating session handover in situations wherethe FMC mobile device 130 has two or more open sessions. In additionalimplementations, the FMC mobile device 130 can be set to attempt tohandover the oldest session (e.g., first initiated session) first, andthe most recent session (e.g., last initiated session) last. In suchimplementations, the MAS 105 and the FMC mobile device 130 can keeptrack of the duration of the sessions open by a device 130. Thus, theMAS 105 can identify which session is being handed over first, and whichsession is being handed over last (and the order of any other sessionsbeing handed over).

In some implementations, one session is active, and another session is“on-hold,” a status in which the user has placed one of the callingparties on hold, while it is actively speaking with another. In someimplementations, to place the session on-hold, the FPN peer CPE 140 a-ccan be operable to process an on-hold request by not transmitting orreceiving media. In other implementations, the FMC mobile device 130 caneffectuate the on-hold status by not sending out any media (or sendingout only background noise generated by the FMC mobile device 130), andalso by discarding any media it receives. In yet other implementations,the FPN peer CPE 140 a-c can be placed in a “send only” state, and theFMC mobile device 130 can be programmed to discard packets it receives;the call's status is that of being on-hold, since the FPN peer CPE 140a-c is not receiving media (i.e., in a send only state), and the FMCmobile device 130 is discarding media it receives.

In some implementations, in a session through the fixed packet network115 between the FMC mobile device 130 and a PSTN peer CPE 150 a-d (orwith the FPN peer CPE 140 a-c) the MAS 105 can be operable to place thesession on hold. The MAS can process an on-hold request from either theFMC mobile device 130 or the peer CPE. In some implementations, the MAScan place the session on hold by, for example, blocking or discardingmedia that it receives from the peer CPE, or by blocking the ordiscarding the media from the FMC mobile device.

To describe an example call handover process of two sessions (oneactive, and one on-hold), the FMC mobile device 130 can have one sessionwith FPN peer CPE 140 a, and another concurrent session with PSTN peerCPE 150 a, wherein both sessions are through the fixed packet networkdomain (i.e., communications for the session are being delivered via thefixed packet network 115). When the link 155 from the access point 145is not strong or begins to degrade (e.g., presence signals are becomingirregular), the FMC mobile device 130 can attempt to hand over bothsessions so as to communicate through the cellular network 110. The FMCmobile device 130 can be operable to identify which session is on hold,and which session is active, and will hand over the on-hold sessionfirst. Because current cellular network implementations only allow oneactive session to be initiated from the same device, if the activesession was handed over first, that session would have to be put on holdbefore another handover request can be initiated. However, it may not bethe desire of the FMC mobile device 130 to put that active session onhold. Thus, handing over the on-hold session first can reduce the numberof on-hold off-hold transactions, and also provide for a more seamlesshandover. One example of a handover process in which the on-hold sessionis handed over first is described in the “Concurrent Call Handover”patent mentioned above.

A condition can arise in which an on-hold communication through thefixed packet network between a peer CPE device communicating with an FMCmobile device is unable to go back to an off-hold status after thehandover of the session to the cellular domain. In prior art cellularnetwork implementations the on-hold or off-hold status of any sessionthrough the cellular network (e.g., cellular network 110) is controlledat the cellular network level; on-hold/off-hold requests are handled bythe cellular network, and an on-hold/off-hold command would not bepassed through the cellular network (e.g., cellular network 110) to theMAS, and subsequently not to any peer CPE. For example, for a sessionbetween the FMC mobile device 130 and a peer CPE (e.g., FPN peer 140a-c, or PSTN peer 150 a-d, or mobile peer 115 a-d) through the cellulardomain, if the FMC mobile device 130 sends an on-hold request to thecellular network, the cellular network processes the request bypreventing the delivery of communications from the FMC mobile device 130to the peer CPE device. Likewise, once an off-hold request is processedby the cellular network, the cellular network would allow packetsbetween the FMC mobile device 130 and the peer CPE devices to flowthrough the cellular network.

To illustrate this situation in which a communication session cannotreturn to an off-hold state, the peer CPE communicating with the FMCmobile device 130 through the fixed packet network 115 can first beplaced on-hold. If the peer CPE is connected to the fixed packet network(FPN peer 140 a-c), it might have been placed in a “send only” mode, forexample. If the peer CPE is connected to the PSTN network (e.g., PSTNpeer 150 a-d), the MAS 105, operating as a gateway, can be instructed toprevent communications between the FMC mobile device 130 and the PSTNpeer 150 a-d, for example. When the session is handed over to thecellular network 110, the FPN peer 140 a-c would still be in a send-onlymode, or the MAS would still be blocking communications between the FMCmobile device 130 and the PSTN peer 150 a-d. If the FMC mobile device130 (now communicating through the cellular network 110 after thehandover) sends a request to take the communication session between thepeer CPE off-hold, the request would not be passed to either the FPNpeer CPE 140 a-c, or to the MAS 105. The FPN peer CPE 140 a-c wouldremain in a send-only state, or the MAS 105 would still be blockingtransmitted media. The users would have to disconnect and requestanother communication session (e.g., in the case of a voice call, makeanother call).

For this situation, in some implementations, prior to sending out thehandover request for an on-hold session between the FMC mobile device130 and a peer CPE (e.g. FPN peer CPE 140 a-c or PSTN peer CPE 150 a-d)can send an off-hold request through the IP network to put communicationsession back on active status prior to the handover (e.g., to startsending and receiving packets). The request can be sent to the MAS 105,which can forward the request to the FPN peer CPE 140 a-c, or therequest can be processed by the MAS 105 to allow communications to flowbetween the FMC mobile device 130 and the PSTN peer CPE 150 a-d. Oncethe handover has occurred, the FMC mobile device 130 can without userinput put the communication back on hold by sending an “on-hold” requestthat is processed by the cellular network 110. Although the FPN peer CPE140 a-c is actually active and can send and receive messages (or the MAS105 is allowing communications between the FMC mobile device 130 and thePSTN peer CPE 150 a-d), the cellular network 110 processes the on-holdrequest by blocking media between the FMC mobile device the otherdevices. When the user desires to take the communication off-hold, theuser can send an off-hold signal from mobile device 130, which is alsoprocessed by the cellular network 110. Because FPN peer 140 a-c (or MAS105) had already been placed in an active state prior to the handover,the removal of the hold at the cellular level would allow communicationsto fully flow. Thus, the handover of this on-hold session involvesmomentarily turning the on-hold session into an active communicationsession, despite the fact that the users desired an on-hold state.Because the handover and immediate blocking of media at the cellulardomain can happen quickly, users might not perceive any media exchangesbetween the mobile device 130 and the CPE 140 a, providing an apparentlyseamless handover of an on-hold session. After the on-hold session hasbeen handed over, any other active sessions can be subsequently handedover as well.

FIG. 2 is an example process 200 that can be performed for administeringthe handover of an on-hold session between an FMC mobile device (e.g.,FMC mobile device 130 of FIG. 1) and a peer CPE device connected to anIP network (e.g., FPN peer CPE 140 a of FIG. 1). The process can beperformed by a mobility application server (e.g., MAS 105 of FIG. 1).The FPN peer CPE can be a broadband modem, for example a DSL modem, abroadband gateway device, cable modem, or cable telephony modem.Communications devices, such as a computer (e.g., laptop, PDA, tablet,etc.) or telephone (e.g., landline telephone or other mobile phone(s)),can be attached to FPN peer CPE. However, other mobile applicationservers, routers, routing devices, and computers can be enabled withsoftware operable to perform the process.

The process 200 can begin at stage 205, wherein a session has beenestablished. The session can be established by the MAS (e.g., MAS 105 ofFIG. 1). The session can be established, for example, as a voice callbetween the FMC mobile device (e.g., FMC mobile device 130 of FIG. 1)and FPN peer device (e.g., FPN peer device 140 a of FIG. 1) through afixed packet network network (e.g., fixed packet network 115 of FIG. 1).

The process 200 can move to stage 210, wherein a request to place thesession between the FMC mobile device and the FPN peer CPE “on hold” hasbeen received. The FMC mobile device (e.g., mobile device 130 of FIG. 1)can send the request to place the session on hold to the MAS (e.g., MAS105 of FIG. 1). The request to place the session “on hold” can bereceived by the mobility application server (e.g., MAS 105 of FIG. 1).The hold request can be initiated by the user pressing one or more keyson the FMC mobile device, thereby indicating that the user wishes toplace the session with the FPN peer CPE on hold. At stage 215, therequest to place the session on hold can be processed. The request canbe processed by the MAS (e.g., MAS 105 of FIG. 1). The MAS can processthe session, for example, by sending or forwarding the on-hold requestto the FPN peer CPE (e.g., FPN peer CPE 140 a of FIG. 1).

As mentioned above, prior to a handover to the cellular domain, the FMCmobile device can send a request to place the FPN peer CPE back toactive state, so that after the handover (after the user requests thatthe session be taken off-hold), the FPN peer CPE can communicate withthe FMC mobile device 130. Thus at stage 220, this request to place FPNpeer CPE (e.g., FPN peer CPE 140 a of FIG. 1) on active status prior tothe handover can be forwarded to the FPN peer CPE. It can be forwardedby the MAS (e.g., MAS 105).

At stage 225, the handover request is received. The handover request canbe received for example from an FMC mobile device (e.g., FMC mobiledevice 130 of FIG. 1) and can be received by the MAS (e.g., MAS 105 ofFIG. 1).

At stage 230, the handover request can be processed. The handoverrequest can be processed, for example, by the MAS (e.g., MAS 105 of FIG.1). In accordance with the handover process described above, a newconnection point is made through the second network (e.g., the wirelessnetwork 110) for the same session, and the previous connection point canbe terminated. Thus, in this example, the MAS-FMC mobile deviceconnection point the cellular network is established, while the MAS-FMCmobile device connection point through the IP network is terminated whenthe connection point in the cellular network is established.

As mentioned above, prior to the handover, the FPN peer CPE was placedon active status, even though the user parties were logically still onhold. To remain on hold after the handover, such that media sent by theFPN peer CPE is not transmitted through the cellular network to the FMCmobile device, and media from the FMC mobile device is not sent to theFPN peer CPE, the FMC mobile device sends a command to the cellularnetwork to place the session on hold.

FIG. 3 shows an example sequence diagram of an implementation in whichthe handover of an on-hold session from the fixed packet network domain(e.g., an IP domain) to the cellular domain (e.g., TDM domain) isconducted, wherein the peer party CPE device 140 a is connected to afixed packet network 115 (e.g., FPN peer CPE 140 a). At stage (1), asession setup is initiated by a message (e.g., a SIP INVITE message)sent from FMC mobile communications device (e.g., FMC mobile device130). In this example, FMC mobile device 130 is within range of awireless access point (for example, wireless access point 145), and thesession setup request is sent via the IP domain (e.g., via fixed packetnetwork 115).

A mobility application server (e.g., MAS 105) can process this requestand at stage (2), the request is directed to an FPN peer CPE 140 a. TheFPN peer CPE 140 a can include separate modules for session setup (e.g.,peer side client) and for transmission/reception of media (e.g., data orVoIP packets).

At stage (3), the session is answered. The session can be answered, forexample, by a CPE 140 a. At stage (4) a confirmation can be sent back tothe mobile communication device 130. The confirmation can be, forexample, a “SIP 200 OK” message. However, other forms of confirmationcan be used based on the particular protocols being used.

Once the session has been established, media data is exchanged at stage(5). The FMC mobile device 130 can exchange media data (in the case of aVoIP call, e.g., voice packets) with the FPN peer CPE 140 a.

The user might want to put the session between the mobile device 130 andthe FPN peer CPE 140 a on hold. At stage (6) the FMC mobile device 130can send a request to the MAS 105 to put the FPN peer CPE 140 a on hold.The request can be in the form of a SIP Invite that is Send-only,meaning that the FPN peer CPE 140 a can send media messages, but notreceive media messages for the current communication session; when thesession is on hold, the mobile device 130 can be operable to discardmedia it receives from the FPN peer CPE 140 a. Thus, when the mediaincludes voice packets, then at stage (7), the CPE 140 a can send voicepacket communications to the mobile device 130, but the user of themobile device will not be able to hear any voice. Moreover, if themobile device 130 sends any packets to the FPN peer CPE 140 a, the FPNpeer CPE 140 a will not be able to receive them because FPN peer CPE 140a is in send-only mode. In this manner, a hold condition can beeffectuated.

If the FMC mobile device 130 moves out of range of the wireless accesspoint 145 (or if the wireless signal is no longer strong), then FMCmobile device 130 at stage (8) can send a message to FPN peer CPE 140 ato take FPN peer CPE 140 a off hold so that FPN peer CPE 140 a can sendand receive media packets. Thus, at stage (9) the session is an activesession again (although logically on hold). At stage 10, the FMC mobiledevice 130 can send out a handover request (e.g., a request to initiatea session) via the TDM domain (e.g., via the cellular network 110). Oncea normal connection is established in the cellular domain, the MAS 105at stage (11) can release the session IP domain. (e.g., terminate theconnection point for the MAS 105-FMC mobile device 130 through the fixedpacket network 115), and send a “BYE” SIP message to the FMC mobiledevice 130. Having handed over the session to the cellular domain, theFMC mobile device 130 and FPN peer CPE 140 a at stage (12) are in anactive session whereby media (e.g., VoIP packets) can be exchangedagain, but now through the cellular network 110. However, because thesession was an on-hold session previously (logically), the FMC mobiledevice 130 at stage (13) will request with the cellular network 110 thatthe session that the session be on hold. As mentioned above, it is thecellular network 110 (not the MAS 105) that controls this hold byblocking messages at the cellular network level. Thus, at stage (14),media can be sent by the peer CPE 140 a, and can be sent by the mobilecommunications device 130, but the communications will not pass throughthe cellular network 110.

A situation can arise, however, in which the active media “Invite”message of stage (8) is not received by the MAS 105, or is lost. Thissituation might occur because the wireless access point 145 is no longerin range. If this situation arises, the FPN peer CPE 140 a is not placedon active status for the session prior to the handover, and once thehandover occurs, remains in a Send-only state. The FPN peer CPE 140 awill be unable to return to an active state should the user desire totake the FPN peer CPE 140 a off hold, because, as mentioned above, incurrent cellular network implementations, off-hold messages areprocessed at the cellular network 110 level and are not communicated tothe MAS 105. Because the MAS 105 is not notified, the message is notcommunicated to the FPN peer CPE 140 a. Thus, the FPN peer CPE 140 a canbe in a send only state for a long time with respect to the session, andthe session might have to be terminated, and new session re-initiated.

FIG. 4 provides an example implementation to address the instance inwhich the SIP active media INVITE of stage (8) might become lost. Theprocess is similar to that of FIG. 2. In FIG. 4, stage (6) of FIG. 2which was a “SIP send only Invite” to place the FPN peer CPE 140 a onsend-only status, is eliminated. Rather, if putting the session on holdis the desired status, the FMC mobile device 130 can discontinue sendingout media, and disregard any packets it receives from FPN peer CPE 140 awhile on hold, as represented by block 405 of FIG. 4. Thus, in the caseof a voice call, neither user will hear voice information, even thoughthe session remains active. When the wireless IP signal begins todegrade or is out of range, and handover occurs, there is no need toplace the FPN peer CPE 140 a back on active after the handover, becausethe session between the FMC mobile device 130 and the FPN peer CPE 140 awas already active. After the handover, the FPN peer CPE 140 a is stillable to send and receive signals, but the on-hold condition remains forstage (10) when the FMC mobile device 130 places an on-hold request tothe cellular network 110. After the FMC mobile device 130 places anoff-hold request, the FPN peer CPE 140 a media can flow through thecellular network 110 again, and can receive media directed at FPN peerCPE 140 a through the cellular network 110.

FIG. 5 is a flow chart of an example process 500 in accordance with FIG.4 for handing over an on-hold session performed by a FMC mobile device(e.g., FMC mobile device 130). The process can begin at stage 505,wherein an active session request can be sent. The active sessionrequest can be sent, for example, by an FMC mobile device (e.g. FMCmobile device 130 of FIG. 1) through an IP network (e.g., fixed packetnetwork 115 of FIG. 1) to a mobility application server (e.g., MAS 105of FIG. 1). The request can signal the setup of a session, such as avoice call, between the mobile device and an FPN peer CPE (e.g., FPNpeer CPE 140 a of FIG. 1).

After the session with FPN peer CPE has been established, at stage 510,an on-hold command is accepted from the user. The on-hold command canbe, for example, initiated by the FMC mobile device based on a depressed“hold” button, a flash of the call button, a voice command from theuser, or some other type of user input indicating a desire to place thesession on hold.

As mentioned above with FIG. 4 and distinguished from the example ofFIG. 5, the FMC mobile device does not send any messages to the FPN peerCPE (for example, a Send-only Invite) to place the session in a holdcondition (or a Send-only condition). Rather, at stage 515 a, becausethe FPN peer CPE device has never been taken off of active, FPN peer CPEcan still send communications to the FMC mobile device, and the FMCmobile device at stage 515 a can still receive media communicated by theFPN peer CPE.

To effectuate the on-hold condition, the FMC mobile device can beoperable to discard the media from the FPN peer CPE at stage. At stage520 a, in the case of a session that is a voice call, the user of theFMC mobile device does not hear any voice from the FPN peer CPE as thosepackets have been discarded by the FMC mobile device.

Additionally, at stage 515 b, in the on-hold condition, any local media(for example, voice) of the FMC mobile device can be received by theoperable module of the mobile communications device. However, this mediawill not be transmitted to the FPN peer CPE since the condition of thesession is still on-hold.

Thus, even though the FPN peer CPE is active and can send and receivemedia, the on-hold condition is still effectuated because the FMC mobiledevice is discarding received packets from the FPN peer CPE and anysubstantive media (e.g., voice) originating at the FMC mobile device isnot being transmitted to the FPN peer CPE.

When the MFC mobile device moves out of the effective range of the IPdomain, for example it moves out of effective range of the wirelessaccess point 145, at stage 525 a request can be sent by the FMC mobiledevice through the cellular network (e.g., cellular network 110) tohandover the on-hold communications session between the FMC mobiledevice and the FPN peer CPE.

After the handover, at stage 530, an on-hold request can be sent by theFMC mobile device to the IP network to place the session between the FMCmobile device and the FPN peer CPE, which had been on hold in the IPdomain, on hold in the cellular domain. Here, the cellular networkhandles the on-hold processing. In other example implementations, tocontinue the on-hold condition between the FMC mobile device and the FPNpeer CPE, instead of sending an on-hold request to the cellular networkfor processing, the mobile communication device can continue to discardmedia received from the FPN peer CPE, and continue to not transmit mediato the FPN peer CPE.

If the user decides to take the session off hold, the FMC mobile devicecan send an off-hold request to the cellular network or in other exampleimplementations can discontinue discarding media received from the FPNpeer CPE and begin transmitting media to the FPN peer CPE.

In the instance that the FMC mobile device is communicating with a peerCPE (e.g., PSTN peer CPE 150 a) connected to the PSTN (e.g., PSTN 120),a similar implementation can be used. The gateway of the mobilityapplication server (e.g., MAS 150) can be operable to control theon-hold call (i.e., prevent messages into and out of the PSTN 120 forthe session with the PSTN peer CPE 150 a). Here, in this implementation,instead of sending a message to the FPN peer CPE to put the session onhold (or sending a Send-only SIP message), the FMC mobile device woulddirect this request at the MAS 105. Referring to FIG. 3, thetransactions of stage (6) and stage (8) would be directed to the MAS 105to place the PSTN peer CPE on hold (or send only status). Just as withthe session between the mobile communication device and FPN peer CPE,the on-hold and off-hold requests in the cellular domain are controlledby the cellular network 110.

FIG. 6 is a block diagram illustrating some components of an example MAS105 or an FMC mobile device 130 operable to facilitate handovers andon-hold/off-hold requests in accordance with the description herein. Thehardware 600 can include a processor 610, a memory 620, a storage device630, and an input/output device 640. Each of the components 610, 620,630, and 640 can, for example, be interconnected using a system bus 650.The processor 610 is capable of processing instructions for executionwithin the system 600. In one implementation, the processor 610 is asingle-threaded processor. In another implementation, the processor 610is a multi-threaded processor. The processor 610 is capable ofprocessing instructions stored in the memory 620 or on the storagedevice 630.

The memory 620 stores information within the device 600. In oneimplementation, the memory 620 is a computer-readable medium. In oneimplementation, the memory 620 is a volatile memory unit. In anotherimplementation, the memory 620 is a non-volatile memory unit.

In some implementations, the storage device 630 is capable of providingmass storage for the device 600. In one implementation, the storagedevice 630 is a computer-readable medium. In various differentimplementations, the storage device 630 can, for example, include a harddisk device, an optical disk device, flash memory or some other largecapacity storage device.

The input/output device 640 provides input/output operations for thedevice 600. In one implementation, the input/output device 640 caninclude one or more of a PSTN trunk interface (e.g., an RJ11 connector),an IP network interface device, e.g., an Ethernet card, a cellularnetwork interface, a serial communication device, e.g., and RS-232 port,and/or a wireless interface device, e.g., and 802.11 card. In anotherimplementation, the input/output device can include driver devicesconfigured to receive input data and send output data to otherinput/output devices, as well as sending communications to, andreceiving communications from various networks.

The MAS and FMC mobile communication device of this disclosure, andcomponents thereof, can be realized by instructions that upon executioncause one or more processing devices to carry out the processes andfunctions described above. Such instructions can, for example, compriseinterpreted instructions, such as script instructions, e.g., JavaScript™(i.e., Java programming language) or ECMAScript™ (i.e.,scripting-language specification) instructions, or executable code, orother instructions stored in a computer readable medium.

Implementations of the subject matter and the functional operationsdescribed in this specification can be provided in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Embodiments ofthe subject matter described in this specification can be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a tangible program carrier forexecution by, or to control the operation of, data processing apparatus.The tangible program carrier can be a propagated signal or a computerreadable medium. The propagated signal is an artificially generatedsignal, e.g., a machine generated electrical, optical, orelectromagnetic signal that is generated to encode information fortransmission to suitable receiver apparatus for execution by a computer.The computer readable medium can be a machine readable storage device, amachine readable storage substrate, a memory device, a composition ofmatter effecting a machine readable propagated signal, or a combinationof one or more of them.

The term “system processor” encompasses all apparatus, devices, andmachines for processing data, including by way of example a programmableprocessor, a computer, or multiple processors or computers. The systemprocessor can include, in addition to hardware, code that creates anexecution environment for the computer program in question, e.g., codethat constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, or a combination of one or moreof them.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, or declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment. A computer program does notnecessarily correspond to a file in a file system. A program can bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub programs, orportions of code). A computer program can be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification areperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output thereby tying the process to a particular machine(e.g., a machine programmed to perform the processes described herein).The processes and logic flows can also be performed by, and apparatuscan also be implemented as, special purpose logic circuitry, e.g., anFPGA (field programmable gate array) or an ASIC (application specificintegrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors(general microprocessors being transformed into special purposemicroprocessor through the application of algorithms described herein),and any one or more processors of any kind of digital computer.Generally, a processor will receive instructions and data from a readonly memory or a random access memory or both. The elements of acomputer typically include a processor for performing instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operablely coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile communications device, atelephone, a cable modem, a set-top box, a mobile audio or video player,or a game console, to name just a few.

Computer readable media suitable for storing computer programinstructions and data include all forms of nonvolatile memory, media andmemory devices, including by way of example semiconductor memorydevices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks,e.g., internal hard disks or removable disks; magneto optical disks; andCD ROM and DVD ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, implementations of the subjectmatter described in this specification can be operable to interface witha computing device having a display, e.g., a CRT (cathode ray tube) orLCD (liquid crystal display) monitor, for displaying information to theuser and a keyboard and a pointing device, e.g., a mouse or a trackball,by which the user can provide input to the computer. Other kinds ofdevices can be used to provide for interaction with a user as well; forexample, feedback provided to the user can be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user can be received in any form, including acoustic,speech, or tactile input.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular implementations ofparticular inventions. Certain features that are described in thisspecification in the context of separate embodiments can also beimplemented in combination in a single embodiment. Conversely, variousfeatures that are described in the context of a single embodiment canalso be implemented in multiple embodiments separately or in anysuitable subcombination. Moreover, although features may be describedabove as acting in certain combinations and even initially claimed assuch, one or more features from a claimed combination can in some casesbe excised from the combination, and the claimed combination may bedirected to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Particular embodiments of the subject matter described in thisspecification have been described. Other embodiments are within thescope of the following claims. For example, the actions recited in theclaims can be performed in a different order and still achieve desirableresults, unless expressly noted otherwise. As one example, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In some implementations, multitasking and parallel processingmay be advantageous.

What is claimed is:
 1. A method for handing over a session between amobile communication device and a customer premises equipment which isconnected to a packet network, the method comprising: sending a sessionrequest through the packet network to a mobility application server,wherein the session is between a mobile communication device and acustomer premises equipment connected to the packet network; initiating,by the mobile communication device, an on-hold command; in response tothe initiation of the on-hold command: receiving media from the customerpremises equipment; discarding the media received from the customerpremises equipment; receiving local media at the mobile communicationdevice; and withholding a transmission of the received local media fromthe mobile communication device; sending a request to hand over thesession between the mobile communication device and the customerpremises equipment through a second network.
 2. The method of claim 1,wherein the packet network comprises a broadband network.
 3. The methodof claim 1, wherein the packet network comprises an IP network.
 4. Themethod of claim 1, wherein the mobile communication device is operableto communicate through a packet network, and also through a cellularnetwork.
 5. The method of claim 1, wherein the mobility applicationserver forwards the session request to the customer premises equipment.6. The method of claim 1, wherein the session request comprises a SIPInvite.
 7. The method of claim 1, wherein handing over the sessioncomprises an establishment of a connection point and a termination of aconnection point.
 8. The method of claim 1, wherein the customerpremises equipment comprises a modem.
 9. The method of claim 1, whereinthe packet network comprises a data over cable network.
 10. The methodof claim 1, wherein the second network comprises a cellular network. 11.A system for handing over a session between a mobile communicationdevice and a customer premises equipment which is connected to a packetnetwork, wherein the system comprises a system processor which isconfigured to: send a session request through the fixed packet networkto a mobility application server, wherein the session is between amobile communication device and a customer premises equipment connectedto the packet network; initiate an on-hold command; in response to theinitiation of the on-hold command: receive media from the customerpremises equipment; discard the media received from the customerpremises equipment; receive local media; and withhold a transmission ofthe received local media; send a request to hand over the sessionbetween the mobile communication device and the customer premisesequipment through a second network.
 12. The system of claim 11, whereinthe packet network comprises a broadband network.
 13. The system ofclaim 11, wherein the packet network comprises an IP network.
 14. Thesystem of claim 11, wherein the mobile communication device is operableto communicate through a packet network, and also through a cellularnetwork.
 15. The system of claim 11, wherein the mobility applicationserver forwards the session request to the customer premises equipment.16. The system of claim 11, wherein the session request comprises a SIPInvite.
 17. The system of claim 11, wherein handing over the sessioncomprises an establishment of a connection point and a termination of aconnection point.
 18. The system of claim 11, wherein the customerpremises equipment comprises a modem.
 19. The system of claim 11,wherein the packet network comprises a data over cable network.
 20. Thesystem of claim 11, wherein the second network comprises a cellularnetwork.